Messaging devices and methods

ABSTRACT

An electronic messaging device includes a receiver configured to receive a message at one of a first operational frequency and second operational frequency. The messaging device can added to a message distribution group comprising a plurality of existing messaging devices. A test communication can be sent through a coupling to test an operation of the messaging device and confirming the addition of the messaging device to the message distribution group without communicating with the existing messaging devices.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of prior application U.S. patentapplication Ser. No. 15/681,518, entitled “MESSAGING DEVICES ANDMETHODS,” filed Aug. 21, 2017, which is a continuation of priorapplication U.S. patent application Ser. No. 15/427,157, entitled“MESSAGING DEVICES AND METHODS,” filed Feb. 8, 2017, which is acontinuation of prior application U.S. patent application Ser. No.14/462,740, entitled “MESSAGING DEVICES AND METHODS,” filed Aug. 19,2014, which is a continuation of prior application U.S. patentapplication Ser. No. 13/758,643, entitled “MESSAGING DEVICES ANDMETHODS,” filed Feb. 4, 2013, the disclosures of which are incorporatedherein by reference in their entireties.

TECHNICAL FIELD

The present application generally relates to the field of wirelesselectronic communications. More specifically, the present applicationrelates to messaging device systems and methods.

BACKGROUND

Paging systems are a reliable and generally inexpensive communicationtool. Paging systems operate on a variety of communication protocols,including the FLEX® protocol by Motorola Inc., which is a four-levelprotocol that presently functions at bit rates of up to sixty-fourhundred bits per second. Generally, the FLEX® protocol reduces thenumber of errors received in transmissions and reduces the possibilitythat a page will be missed or garbled to the point where it isunreadable or unusable. Further, it allows for a relatively large numberof end users to be supported.

The modulation range of FLEX® is plus and minus forty-eight hundredkilohertz of deviation. FLEX®'s four levels are defined as −4,800 hertz,−1,600 hertz, +1,600 hertz, and +4,800 hertz, with reference to theoperating frequency. Each level represents two bits in a giventransmission. They represent ‘00’, ‘01’, ‘11’, and ‘10’ respectively.

Additionally, FLEX® allows for the adjustment of bit rate based upon thechannel loading, operating at 1,600, 3,200, or 6,400 bits per second.FLEX® can switch between four level and two level operation as needed,which can improve paging quality during times of low or reduced activityand increase channel capacity during times of high traffic.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a messaging device in accordance with onenon-limiting embodiment.

FIG. 2 depicts an example messaging device along with a representationof an example graphical user interface menu tree.

FIG. 3 depicts an example system diagram of a messaging device incommunication with a host via an Over-the-Internet-Programming (OTIP)technique.

FIG. 4 depicts an example process for execution by a messaging devicecoupled to a computing device.

FIG. 5 depicts an example process for execution by a computing devicethat is coupled to a messaging device.

FIG. 6 depicts an example flow diagram for determining when adual-frequency messaging device operating on a synchronous pagingprotocol is to change from a primary frequency to a secondary frequency.

FIG. 7 depicts an example flow diagram for determining when adual-frequency messaging device operating on a synchronous pagingprotocol is to change from a secondary frequency to a primary frequency.

FIGS. 8A-8B depict example operational diagrams of a messaging devicechecking received signal strength indication (RSSI) levels.

FIG. 9 depicts time-based operational frequency changes of a messagingdevice in accordance with one non-limiting embodiment.

FIG. 10 depicts a messaging device determining a filtered average RSSIlevel in accordance with one non-limiting embodiment.

FIG. 11 depicts three example operational scenarios for a messagingdevice that is operating at a local (primary) frequency.

FIG. 12 depicts three example operational scenarios for a messagingdevice operating at a wide area (secondary) frequency.

FIG. 13 depicts a system block diagram of a messaging device in wirelesscommunication with a computing device.

FIG. 14 depicts an example block diagram of a server in communicationwith a computing device and a messaging device.

DETAILED DESCRIPTION

Although the following text sets forth a detailed description ofnumerous different embodiments, it should be understood that the legalscope of the description is defined by the words of the claims set forthat the end of this disclosure. The detailed description is to beconstrued as exemplary only and does not describe every possibleembodiment since describing every possible embodiment would beimpractical, if not impossible. Numerous alternative embodiments couldbe implemented, using either current technology or technology developedafter the filing date of this patent, which would still fall within thescope of the claims.

Throughout this disclosure, references to components or modulesgenerally refer to items that logically can be grouped together toperform a function or group of related functions. Components and modulescan be implemented in software, hardware, or a combination of softwareand hardware. The term software is used expansively to include not onlyexecutable code, but also data structures, data stores and computinginstructions in any electronic format, firmware, and embedded software.It should be noted that although examples discussed below might describespecific features or functions as part of a specific component ormodule, those features or functions may be implemented as part of adifferent component or module.

The examples discussed below are examples only and are provided toassist in the explanation of the systems and methods described. None ofthe features or components shown in the drawings or discussed belowshould be taken as mandatory for any specific implementation of any ofthese systems or methods unless specifically designated as mandatory.For ease of reading and clarity, certain components, modules, ormethods, may be described solely in connection with a specific figure.Any failure to specifically describe a combination or subcombination ofcomponents should not be understood as an indication that anycombination or subcombination is not possible. Also, for any methodsdescribed, regardless of whether the method is described in conjunctionwith a flow diagram, it should be understood that unless otherwisespecified or required by context, any explicit or implicit ordering ofsteps performed in the execution of a method does not imply that thosesteps must be performed in the order presented and may be performed in adifferent order or in parallel.

The presently disclosed system and methods generally relate to messagingdevices, such as pagers, and associated systems that can be used in avariety of operational environments, including the medical industry. Forexample, the systems and methods as disclosed herein can be used inconnection with messaging devices deployed in a geographically dispersedarea, such as a college campus, airport, or seaport, that allow anauthorized party to issue almost instantaneous updates on criticalevents, such as a terrorist strike or a natural disaster, thoughmessages sent via a communication network. Thus, while many of theembodiments described herein are in the context of the medical industry,it is to be appreciated that such disclosure is merely illustrative andthat the systems and methods disclosed herein are applicable across awide range of operational environments.

The messaging devices described herein operate using a time synchronizedprotocol, such as the FLEX® paging protocol, or other suitable timesynchronized protocol. Generally, with a time synchronized protocol thereceiving device uses transmitted data to maintain synchronization. Thetime synchronized protocol provides data at precise time intervalsallowing the receiver to monitor and adjust timing as needed. Bycomparison, with asynchronous protocols, a preamble is transmitted for alength of time to guarantee that all messaging devices with thatasynchronous protocol can “wake-up” or lock to the signal. The addedpreamble waste air time and can force messaging devices to keep theirreceiver circuits energized until a synchronization word is detected.Thus an asynchronous protocol is generally less efficient than a timesynchronized protocol at the same data rate, since the time spenttransmitting a preamble in an asynchronous protocol can be time used totransmit other types of data in a synchronous protocol.

Messaging devices described herein can be one-way devices or two-waydevices. Two-way devices can utilize a return channel to provideinformation to the network, such as the location of the messagingdevice, message state, or an alphanumeric message, for example. Suchdevices can use any suitable protocol for these transmissions, such asthe ReFLEX® paging protocol (Motorola, Inc.), a WiFi-based protocol, ora Bluetooth-based protocol. In some embodiments, as described in moredetail below, the messaging device may be in wireless communication witha smart phone, or other portable communications device, of an end uservia a suitable data communications link.

The systems and methods described herein generally provide numerousfeatures that seek to improve the experience of the end user of amessaging device and/or a network administrator, including, for example,dual-frequency capability, over-the-internet-programming (OTIP), aUniversal Serial Bus (“USB”) interface, battery savings techniques,and/or message encryption.

With regard to dual-frequency capability, messaging devices inaccordance with the systems and methods described herein can operate onmultiple frequencies utilizing any suitable protocol, such as the FLEX®,ReFLEX® protocol, or other suitable time synchronous protocol. Intypical hospital operational environments, for example, in-house orcampus-wide paging networks operate on a frequency that is separate fromthe wide-area frequencies provided by narrowband paging carriers. Byutilizing dual-frequency capability, the messaging devices describedherein generally combine the speed and reliability of an in-house systemwith the wide area footprint of a commercial paging carrier, since themessaging device is operating on both frequencies simultaneously. Someembodiments of the messaging devices can operate on more than twofrequencies.

With regard to OTIP, messaging devices in accordance with the systemsand methods described herein seek to improve the efficiency for networkadministrators and end users by allowing certain pager features to beprogrammed or updated over the internet by way of a network connection.Therefore, the necessity for an end user to bring or send theirmessaging device to a centralized location (or to a vendor) if certainpager programming is required can be reduced or even eliminated. In someembodiments, as described in more detail below, an end user can couple amessaging device to a computer to accept programming commands. Via asoftware application executed on the computer, for example, networkadministrators can send programming commands through the Internet to theend user's messaging device. Additionally, when the messaging device iscoupled to the computer, the messaging device can upload messages fromthe messaging device to the computer for storage. In some embodiments,when the messaging device is coupled to a computer, the last fiftymessages (or other desired number of messages) that were received by themessaging device will upload into a software application executed on thecomputer and can be subsequently routed to the network administrator forviewing and storage purposes. In order to preserve messaging forauditing or for other purposes, in various embodiments, messages storedlocally on the messaging device can be deleted from the display screenby the end user but cannot be deleted from local storage on themessaging device until they are uploaded for storage.

The messaging device can interface with the computer using any suitabletype of wired or wireless interface. In one embodiments, a UniversalSerial Bus (USB) interface is utilized which allows an electrical chargeto be delivered to a rechargeable battery, and a connection for localPaging Programming Software (“PPS”) on the computer and access to OTIP.As is to be appreciated, a variety of different communication protocolscan be used without departing from the scope of the present disclosure,such Bluetooth® protocols, for example.

Messaging devices in accordance with various embodiments of the presentdisclosure can provide message encryption, as is emerging as arequirement within certain operational environments, such as hospitalenvironments, for example. Thus, sensitive patient information, or otherprivate information, can be sent over paging networks described hereinin encrypted formats. In some embodiments, the Secure Paging Layer (SPL)protocol from Critical Response Systems™ using AES-128 encryption can beused. Additional spoilers may be added for additional security. Detailsregarding the SPL protocol can be found in Secure Paging Layer ProtocolSpecification, Version 0.9, February 2012, which is incorporated hereinby reference. Updates to the encryption keys associated with theencryption protocol can be received via Over-the-Air-Programming (OTAP)or via OTIP, as described in more detail below. In some embodiments,Critical Security Parameters (CSP) such as passcodes and encryption keyscan have counters associated with them counting the number of timesused, how much time has elapsed since updates and how often a CSP isrejected. CSPs can be are stored in memory on the messaging device in ascrambled or interleave fashion. In some embodiments, the messagingdevice can receive a destruct command, either via OTAP or OTIP that willclear all messages from the device and render the device useless.

In some embodiments, a messaging device can include a rechargeable powersupply that is chargeable via a micro-USB port. Other embodiments,however, utilize disposable batteries or other type of power source. Inany event, various power consumption techniques described herein seek toincrease the life of the message device, thereby seeking to reduce theneed to charge the messaging device via an external power source or theneed to replace the disposable batteries.

FIG. 1 is a block diagram of a messaging device 100 in accordance withone non-limiting embodiment. The messaging device 100 can include anantenna system 102 coupled to a receiver 104. The antenna system 102 caninclude a Low Noise Amplifier (LNA) to amplify received signals. Theantenna system 102 can also permit multi-frequency operation, asdescribed in more detail below. Some embodiments can have multiplereceivers 104 n which can be used to scan for multiple operationalfrequencies. A controller 108, such as a small ARM™ embedded controller,for example, can be programmed to manage the user interface and otherfunctionality of the messaging device 100. In some embodiments, adecryption engine 110 can utilize encryption keys 112 for the decryptionof various messaging received by the messaging device 100. Updates toencryption keys 112 can be received via OTAP and/or OTIP. A display 114can be used to display text or graphical messages. In one embodiment, aliquid crystal display may be used. As is to be readily appreciated,other types of suitable displays, such as touch-screen displays, can beused. An audible alarm 116 can be used to audibly draw attention toreceipt of a message or other notifications. A light source 118 can beused to visually draw attention to receipt of a message or othernotifications. In some embodiments, the light source comprises one ormore light emitting diodes (LEDs), or other type of light source,capable of selectively providing a visual indication. An input device120 can allow for a user to interact with the messaging device 100 toscroll through messages, select messages, or delete messages, forexample. The input device 120 can include navigational arrows, an“enter” key, and so forth. An optional backlight (not depicted) mayallow use in low-light conditions.

The messaging device 100 can also include one or more interfaces whichsupport data exchange between the messaging device 100 and a computingdevice, which can be any type computer device suitable for communicationover the network, such as a tablet computer, a laptop computer, netbookcomputer, desktop computer, and so forth. An example interface isillustrated as a Universal Serial Bus (USB) electrical interface 122.The USB electrical interface 122 can include, for example, astandard-USB or a micro-USB port. Alternatively, or additionally, themessaging device 100 can include a wireless interface 124 to allow forwireless transfer of data between the messaging device 100 and anothercomputer device. The wireless interface 124 can include a Bluetooth®module, a ZigBee® module, or a Wi-Fi™ module, for example.

Still referring to FIG. 1, a memory 126 can include volatile ornon-volatile memory. Volatile memory units can include random accessmemory (RAM), for example. Non-volatile memory units can include readonly memory (ROM), for example, as well as mechanical non-volatilememory systems, such as, for example, a hard disk drive, etc. The RAMand/or ROM memory units can be implemented as discrete memory ICs, forexample. The memory 126 can include program memory, message storage, orboth. One or more device identifiers 128 can be used by the controller108 to select signals intended for itself. The device identifiers 128can be Channel Access Protocol (CAP) codes, as illustrated. The deviceidentifiers 128 can include a unique identifier so that the messagingdevice 100 can be sent an individually-targeted message.

A power source 130 can be non-removably mounted in the messaging device100. The power source 130 can be, for example, a 1100 milliamps-per-hour(“mAh”) Lithium Ion rechargeable battery or a 500 mAh Lithium Ionrechargeable battery. The power source 130 can be in communication witha charging system 132 that, for example, is configured to receive energyfrom the USB electrical interface 122. In one embodiment, the chargingsystem 132 is an inductive charger. It is noted that some embodiments ofthe messaging device 100 can utilize other power sources, such asdisposable batteries. The charging system 132 can utilize a hardware orsoftware “fuel gauge” to track the power source's relativestate-of-charge (SOC). In some embodiments, a visual indication of theSOC is graphically provided on the display 114. The visual indicationcan be a percentage of battery life remaining and/or a dynamic image ofa battery that changes based on charge, for example. An audio indictorcan also be used, such as a repeating chirp, to indicate a low batterylevel.

FIG. 2 depicts an example messaging device 200 along with arepresentation of an example graphical user interface menu tree 220. Themessaging device 200 comprises a body 214 which houses variouscomponents, such as an input device 202, a display 204, and a lightsource 206. The messaging device 200 can also include an audibleindicator or vibratory indicator (not shown). The sound level producedby the audible indicator can be selected based on operationalenvironments. In some implementations, the sound level generated by theaudible indicator may reach at least 85 dB at a range of 12 inches fromthe messaging device 200. In other implementations, the sound levelgenerated by the audible indicator may reach at least 95 dB at a rangeof 12 inches from the messaging device 200. In any event, a user of themessaging device 200 can select from a variety of different alert tones,and in some embodiments, assign particular alert tones to particular CAPcodes or other types of addresses programmed in the device. A port 212,such as a data/charging port, can be positioned in a suitable locationon the messaging device 200 to allow the messaging device 200 to beselectively coupled to another computing device. The data/charging port212 can be a micro-USB port, for example. The messaging device 200 canhave any suitable configuration or form factor. In one embodiment, themessaging device 200 is a key fob or other easily carried accessory. Inanother embodiment, the messaging device 200 is permanently attached to,or otherwise coupled with, a university-issued room key or access card(not depicted), so that a student will necessarily have the device withhim or her at all times.

The graphical user interface menu tree 220 can be arranged in a nestedmenu format, as shown, or any other suitable arrangement. While FIG. 2depicts one example arrangement, such arrangement is merely forillustrative purposes as a wide variety of other arrangements can beused without departing from the scope of the present disclosure. The toplevel menu can include a variety of options, such as message 222,folders 224, settings 226, status 228 and about 230, which can benavigated using the input device 202. Selecting, or accessing, one ofthe options can provide a user with additional choices. As described inmore detail below, various settings and parameters of the messagingdevice can be updated or changed using OTIP.

Receiving an input to select messages 222, for example, takes the userto a received message landing screen. Arrow keys of the input device 202can scroll up and down through message lists. The right arrow buttoncan, for example, take the user to a screen that views the relatedmessage. Additional message options can include a delete message option.When the message is deleted it is removed from the message display listusing this option, however, it may still remain stored local to themessaging device 200 (such as within memory 126 shown in FIG. 1) forlater retrieval via the USB interface, provided that the max number ofmessages has not been exceeded. Other message options can includelocking a message and marking a message as unread, as illustrated.

Receiving an input to select folders 224 can take the user to a list ofall folders on the messaging device 200. In some embodiments, themessaging device 200 can locally store a relatively large number ofmessages. For example, some embodiments can be capable of storing inexcess of 50 messages. Some other embodiments can be capable of storingin excess of 100 messages. Other embodiments can be capable of storing200 or more messages. As the number of stored messages increases, thereis a need to efficiently navigate, control and access the storedmessages while using the input device 202 and the display 204. Themessaging of messaging device 200 shown in FIG. 2 utilizes a collectionof message lists, each list of which is viewable view the display 204.In the illustrated embodiment, the messaging device 200 includes a“message view list,” an “unread message list,” a “locked message list,”an “all message list,” and a “deleted messages list.” Messages stored inthe memory (such as memory 126, FIG. 1) of the messaging device 200 willappear in one or more of these lists.

Exemplary guidelines for populating the lists will now be described. Asis to be appreciated, the particular guidelines may vary based onimplementation. The “Message view list” is a list of the last X numberof received messages, where X is settable (e.g., 10, 25, etc.), exceptdeleted messages. “Unread message list” is a list of all unread messagesfrom the total list of stored messages. “Locked message list” is a listof all of the locked messages from the total list of stored messages. Insome embodiments, a maximum number of locked messages may be set. Lockedmessages are not automatically deleted. “All Message List” is a list atall messages stored in the device, including deleted messages. Deletedmessages are shown in “All Message List,” but are not shown in the“Message View List.” By navigating through the various lists, the useroperating the messaging device 200 can access and control the relativelylarge number of messages that can be stored locally on the device.

It is noted that the folders 224 can be defined or structured in anysuitable fashion. For example, some embodiments of the messaging device200 can arrange messages by CAP code Name, such as “Office,” “CodeBlue,” and “Sports.”

The messaging device 200 can have multiple address parameters called CAPcodes. In some embodiments, each CAP code can be designated of one ofthree types: Personal, Group or Maildrop. The personal CAP code is usedfor a main address. These types of CAP codes are for messages directedat only messaging device 200. A group CAP code can be a common CAP code(sometimes referred to as a “burned in CAP code” or a “hardwired CAPcode) that are programmed in to multiple messaging devices. Common CAPcodes allow for only one message to be sent out and have multiplemessaging devices receive the same message at generally the same time.This is typically referred to as “One-to-Many” addressing. Maildrop CAPcodes can be used for Information Services (IS). These CAP codes canreceive daily, weekly type information feeds where history is notrequired. For each of these types of CAP codes a number of “MaxMessages” can be set. As is to be readily appreciated, other messagesdevices in accordance with the systems and methods described herein canuse different or alternative addressing techniques or protocols besidesCAP codes, such as addressing based on an electronic serial number, forexample. As such, CAP codes, as used herein, are merely one exemplaryaddressing technique.

Receiving an input to select settings 226 can allow the user to set orview various control parameters on the messaging device 202, examples ofwhich are shown in FIG. 2. Receiving an input to select status 228allows a user to view various operational parameters, as well as modifyvarious operational parameters. In particular, the Channel Frequenciesparameter of the System Config menu frequency can list the twofrequencies that are set for dual-frequency operation. The Channel Modeparameter can list, for example, the current mode of operation alongwith the current frequency that the messaging device 200 is listeningon. Addresses and Color Code can list the CAP Codes and their associatedcolor code, priority and CAP code Name. The System Collapse parametercan display the last received system collapse value. The FLEX® timeparameter can display the last received FLEX® time from the network. Themessaging device 200 can also include other various options, such as anAbout option 230, which can display a message on the display 204 whenactivated. The message can include a settable, or programmable, portionthat be updated via the OTIP or OTAP functionality, as described in moredetail below.

FIG. 3 depicts an example system diagram of a messaging device 302 incommunication with a host 322 via an OTIP technique. The messagingdevice 302 is electrically coupled to a computing device 310 via acommunications link 306. In the illustrated embodiment, thecommunications link 306 is a USB cable that is selectively placed inelectrical communication with an USB interface 304 of the messagingdevice 302 and a USB interface 308 of the computing device 310. Otherforms of communications links can be utilized, such as Bluetooth® orNear Field Communication (NFC) protocols, for example. In addition toserving as a data communication link between the messaging device 302and the computing device 310, the communications link can also serve todeliver energy to the messaging device 302 to charge the power source(such as power supply 130 in FIG. 1).

The computing device 310 can be any suitable processor-based device orsystem, such as a personal computer, laptop, server, mainframe, or acollection (e.g., network) of multiple computers, for example. Thecomputing device 310 can include one or more processors 312 and one ormore computer memory units 314. For convenience, only one processor 312and only one memory unit 314 are shown in FIG. 3. The processor 312 mayexecute software instructions stored on the memory unit 314 to executean account manager application 316. The processor 312 may be implementedas an integrated circuit (IC) having one or multiple cores. The memory314 may include volatile and/or non-volatile memory units. Volatilememory units may include random access memory (RAM), for example.Non-volatile memory units may include read only memory (ROM), forexample, as well as mechanical non-volatile memory systems, such as, forexample, a hard disk drive, an optical disk drive, etc. The RAM and/orROM memory units may be implemented as discrete memory ICs, for example.

The computing device 310 can be in electrical communication with a host322 via a networked connection 320, such as an Internet-based connectionthrough a network interface 318. The host 322 can include a server 324for facilitating the transmission of commands, instructions, or otherdata to be sent to the messaging device 302 via the computer device 310.Such communications can be encrypted or otherwise secured using suitableencryption protocols. A network administrator can interact with the host322 to selectively decide which commands will be sent to particularmessaging devices. Such commands can include, without limitation,changes to the parameters/settings of the messaging device (such asvarious settings illustrated in the interface menu tree 220 of FIG. 2),updates to firmware of the messaging device, changes to CAP codes,and/or adding additional encryption keys. A CAP code database 328 can beused to store information regarding various messaging devices associatedwith the host 322. With regard to the firmware of the messaging device302, it is noted that in some embodiments the computer device 310 canupgrade the firmware using the account manager application 316.

Messages, or other information, stored local to the messaging device 302can be uploaded to the computing device 310 and/or the host 322 once thecommunications link 306 is made. The host 322 can receive messages fromthe messaging device 302 and store them in suitable storage media, suchas a message database 326. The account manager application 316, or othersuitable software application, executed by the computer device 310 canfacilitate the uploading or transferring of the messages.

FIG. 4 depicts an example process 400 for execution by a messagingdevice that is coupled to a computing device. At 402, the messagingdevice is electronically coupled to a computing device. As describedabove, this electronic coupling may be a USB-based coupling, awireless-based coupling, or any other suitable form of coupling thatallows data transfer between the messaging device and the computingdevice. At 404, programming commands are received on the messagingdevice that have been sent from the computing device. These programmingcommands could include, for example, an update to firmware or encryptionkeys. At 406, messages stored locally to the messaging device can betransmitted to the computing device. At 408, after the messaging devicehas been added to a particular message distribution group, a testmessage can be received at the messaging device that is associated withthat particular message distribution group. In other words, the testmessage is dropped into the firmware of the message device so that itcan attempt to process the test message as if it was received via anover-the-air transmission. At 410, upon successful receipt of the testmessage, receipt is indicated. The processes at 408 and 410 beneficiallyallow for a message distribution group update to be confirmed withoutnecessarily having to globally transmit a test message to all messagingdevices associated with that message distribution group. Instead, usingthe OTIP techniques described herein, such updates can be confirmed viaa test message sent only to the firmware of a messaging device coupledto a computer device. Such testing techniques generally allow forconfirming that a messaging device has been successfully added to aparticular message distribution group without having to inconvenientlybroadcast a test page to all members of the message distribution group.

FIG. 5 depicts an example process 500 for a computing device that iscoupled to a messaging device. At 502, the computing device iselectronically coupled to a messaging device. As described above, thiselectronic coupling may be a USB-based coupling, a wireless-basedcoupling, or any other suitable form of coupling that allows datatransfer between the computing device and the messaging device. Thecomputing device can be executing a suitable application such as pagerprogramming software (PPS) and is in communication with a host via anetworked connection. At 504, programming commands are received from thehost. These programming commands could include, for example, an updateto firmware or encryption keys. At 506, the programming commands aresent to the messaging device. At 508, messages are received from themessaging device. The messages can be stored locally at the computingdevice and/or at 510, transmitted to the host. At 512, after themessaging device has been added to a particular message distributiongroup a test message can be sent to the messaging device that isassociated with that particular message distribution group.

Various messaging devices in accordance with the systems and methodsdescribed herein utilizing a time synchronous paging protocol, such asFLEX®, have a dual frequency mode that generally allows a firstfrequency to be set as primary frequency and a second frequency as asecondary frequency. The device will stay on the primary frequencyunless the primary frequency is determined to be lost or otherwise nolonger acceptable for use. The primary frequency can be associated witha local transmission station and the secondary frequency can beassociation with a wide-area transmission station. As described in moredetail below, various decision making processes based on settablevariables and real-time data can be used by the messaging device tocontrol the switching between the available frequencies.

FIG. 6 depicts an example flow diagram 600 for determining when adual-frequency messaging device operating on a synchronous pagingprotocol is to change from the primary frequency (shown as “localfrequency ”) to the secondary frequency (shown as wide-area frequency”).In some embodiments, the primary frequency and the second frequency areboth within the range of 929-932 MHz. The flow diagram 600 can beexecuted by software residing in memory 126 (FIG. 1), for example. Ingeneral, the flow diagram 600 tracks conditions that favor eitherkeeping the messaging device at the primary frequency (such ascontinually strong signal strength at the primary frequency, forexample) and conditions that favor switching the operating frequency(such as a lack of synchronization signal or a continually weak signalstrength at the primary frequency).

At 602, a messaging device is running at the local frequency. At 604,which can occur after a reset or device power up, for example, it isdetermined if a synchronization signal is detected at the messagingdevice. If the synchronization signal is not detected, a variable isincremented at 606 (shown as Lost Sync Count). If the synchronization isnot detected within a particular time period, which can be determinedbased on the value of the Lost Sync Count variable, the messaging deviceis switched to operate at the wide area frequency at 626. The timeperiod is shown as 67.5 seconds, which is merely one example time periodand coordinates to the time period associated with 36 frames in theFLEX® protocol, which are broadcasted at intervals of 1.875 seconds.FIG. 9, below, illustrates an example switching of operationalfrequencies based on the lack of synchronization during a definedperiod. Referring again to 604, if a synchronization frame is detected,a variable related to lost synchronization (e.g., “Lost Sync Count”) iscleared at 608. After the synchronization frame is detected at 604, itis determined at 610 if another synchronization frame is detected at themessaging device. If the synchronization is not detected within aparticular time period at 622 (shown as 67.5 seconds, which, again, ismerely one example time period), the messaging device is switched tooperate at the wide area frequency at 626. If a synchronization frame isdetected at 610, the process proceeds to analyze the signal to determineits usefulness.

In the illustrated embodiment, at 612, the received signal strengthindication (RSSI) value of the received signal is analyzed to determineif it falls within a particular target range. In one embodiment thetarget range is −60 dBm and −120 dBm. Other target ranges can be used.As is to be readily appreciated, other ranges of RSSI values can beused. If the RSSI value is within the range, at 614, the signal may beusable and a filtered average RSSI value is calculated. If the RSSIvalue is not within the target range, the process returns to 608. In theillustrated embodiment, an average of five RSSI values, excluding theminimum and maximum RSSI values, is determined. In other words, in aneffort to reduce spurious or overly frequent frequency changes, the RSSIcannot be used to initiate frequency change until a certain quantity ofRSSI values have been received. At 616, it is determined how thefiltered average RSSI value compares to a RSSI threshold. The RSSIthreshold in the illustrated embodiment is −110 dBm. If the average RSSIvalue is greater than the RSSI value (indicative of a relatively strongsignal), the process proceeds to 618, where a variable is incrementedand it is determined if the variable exceeds a threshold. In theillustrated embodiment, the variable is shown as “Local to Wide Clear”and the threshold is set at three. When the threshold is exceeded, whichindicates the presence of a continually strong signal, the processproceeds to 620 where various variables, including “Local to Wide Clear”and “Local to Wide Clear Count” are set to zero. Referring again to 616,if the average RSSI value is less than the RSSI value (indicative of arelatively weak signal), the process proceeds to 624, where a variableis incremented and it is determined if the variable meets or exceeds athreshold. In the illustrated embodiment, the variable is shown as“Local to Wide” and the threshold is set at three. If the threshold ismet or exceeded, which indicates the presence of a continually weaksignal at the primary frequency, the messaging device is changed tooperate at the secondary frequency at 626 (shown as the wide areafrequency). Example operational scenarios illustrating the hysteresiseffect of the processing blocks 616, 618, 620 and 624 is shown below inFIG. 11.

FIG. 7 depicts an example flow diagram 700 for determining when adual-frequency messaging device operating on a synchronous pagingprotocol is to change from the secondary frequency (shown as “wide-areafrequency”) to the primary frequency (shown as “local a frequency”). Theflow diagram 700 can be executed by software residing in memory 126(FIG. 1), for example.

At 702, a messaging device is operating a wide-area frequency. Suchoperation can be based on a change to the wide-area frequency initiatedat 626 (FIG. 6). At 704, it is determined if synchronization can beestablished with the wide-area frequency. At 706, it is determinedsynchronization is established within a certain time period. In theillustrated embodiment, the time period is 67.5 seconds, although thisdisclosure is not so limited. If the wide-area frequency synchronizationsignal is not received within the time period, the messaging device ischanged to operate at the local frequency at 714. The process flow canthan resume at 602, as shown in FIG. 6. As is to be appreciated, whileflow diagram 700 and flow diagram 600 refer to particular time periods,such time period can be a function of a variable incremented at certainintervals, such the variable named Lost Sync Count of FIG. 6 and FIG. 7.For example, a variable may be incremented every 1.875 seconds. After 26increments, a time period of 48.75 seconds will have elapsed, after 36increments, a time period of 67.5 seconds will have elapsed, and soforth. Therefore, the various time periods referred to herein caneffectively be monitored by tracking the value of a variable that isincremented at known timed intervals.

If a synchronization signal on the wide-area frequency was detected at704, the Lost Sync Count variable is reset at 708. If anothersynchronization signal on the wide-area frequency is not detected at710, the process proceeds to 712, where the Lost Sync Count variable isincremented to indicate the passage of time. If 67.5 seconds (or othersuitable time period) has elapsed without detected a synchronizationsignal, the messaging device changes to operate at the local frequencyat 714. If another synchronization signal on the wide-area frequency isdetected at 710, the process proceeds to 718, where the messaging deviceis switched to operate on the local (or primary) frequency. Afterswitching to the local frequency, parameters associated with the localfrequency levels can be analyzed to determine the appropriate course ofaction. At 720, the RSSI value of the local frequency is analyzed todetermine if it falls within a particular range, which is shown as −60dBm to −120 dBm although other embodiments can use different ranges. Ifthe RSSI of the local frequency is not within the range, it is not ausable signal and the messaging device is changed back to operating onthe wide-area frequency at 716. If the RSSI of the local frequency iswithin the range, the filtered average RSSI value can be determined at722 once a requisite number of RSSI values have been determined.

At 724, the average RSSI value is analyzed to determine its relativestrength. If the average RSSI value is greater than or equal to athreshold (shown as −103 dBm in the illustrated embodiment), a variableis incremented at 726 indicating a favorable local frequency signalstrength is present. When the value of the variable meets or exceeds athreshold (shown as 3 in the illustrated embodiment), the messagingdevice can continue to operate at the local frequency, as indicated at714. If the average RSSI value at 724 is not greater than or equal to athreshold (shown as −103 dBm in the illustrated embodiment), it mayindicate a relatively weak local signal. A variable tracking thiscondition, shown as “Wide to Local Clear,” can be incremented. At 728,the value of this variable is checked and if it is greater than orexceeds a threshold (which could indicate a relatively long period ofweak local signal strength), various variables are reset to zero at 730.Example operational scenarios illustrating the hysteresis effect of theprocessing blocks 722, 724, 726, 728, and 730 is shown below in FIG. 12.

FIGS. 8A-8B depict example operational diagrams of a messaging devicechecking RSSI levels. The illustrated embodiments show actions taken atT0, T1 . . . T5, where each interval is separated by 1.875 seconds,which coordinates with length of the frames transmitted in the FLEX®data format. Other embodiments can use different timing intervals.Generally, the messaging device wakes-up every 1.875 seconds and if asynchronization signal is detected, the RSSI level is checked. FIG. 8Ashows a messaging device operating on a primary frequency (e.g., a localfrequency) and FIG. 8B shows a messaging device operating on a secondaryfrequency (e.g., a wide-area frequency). FIGS. 8A-8B depict a selectedRSSI target range of −120 dBm to −60 dBm, which coordinates with theprocess blocks 612 and 720 in FIGS. 6 and 7, respectively. As is to beappreciated, different RSSI target ranges can be used. In any event,FIG. 8A depicts the messaging device checking the RSSI of the localfrequency at T0, T1 and T5 upon detecting the synchronization signal.The RSSI level at T0, T1 and T5 are all shown to be within the RSSIoperating range, which indicates the local frequency may be usable. Bycomparison, the RSSI levels at T3 and T4 are not within the RSSIoperating range. Accordingly, the local frequency is deemed notavailable for those intervals, as indicated in FIG. 8A. With referenceto FIG. 8B, the RSSI check that is performed can be a check of the localRSSI level. Accordingly, the RSSI levels measured at each time intervalin FIG. 8A and FIG. 8B are shown to be the same.

FIG. 9 depicts time-based operational frequency changes of a messagingdevice in accordance with one non-limiting embodiment. Generally, when amessaging device is reset or powered on, the messaging device will tryto receive a synchronization signal on its local frequency. In theillustrated embodiment, synchronization signals are not received any ofthe time periods (illustrated as 67.5 seconds). At T1, the messagingdevice changes its operational frequency from the local frequency to thewide-area frequency in an attempt to synchronize. After 67.5 seconds (orother suitable time frame), the messaging device changes its operationalfrequency from the wide-area frequency back to the local frequency. Asshown, the process of switching operational frequencies can continue asthe time periods for detecting synchronization signals expire.

FIG. 10 depicts a messaging device determining a filtered average RSSIlevel in accordance with one non-limiting embodiment. As illustrated,the RSSI level is measured at time intervals T0, T1 . . . T9 based onthe receipt of the synchronization signals. The RSSI levels at T2 and T6are not within the RSSI target range (shown as −120 dBm to −60 dBm), andaccordingly are not used in the calculation. In the illustratedembodiment, the messaging device seeks to obtain an average RSSI valuewithin a suitable range before the operational frequency of the deviceis switched. The RSSI levels used in the calculation are also filteredto remove the minimum and maximum values from the calculation. Othertechniques for filtering/averaging the RSSI levels can be used. Asillustrated, the RSSI level measured at T0 is deemed the minimum valueand the RSSI level measured at T3 is the maximum value. Accordingly,these RSSI levels are not used in the calculation. The RSSI levels atT1, T4, T7, T8 and T9 are averaged by adding them together and dividingby five to reach a filtered average RSSI value of −100 dBm. Thisfiltered average RSSI value can be compared against a RSSI triggerthreshold to determine if the operational frequency should be changed.As illustrated in FIG. 6 and FIG. 7, the level of the this RSSI triggerthreshold may a first level when the messaging device is operating inthe primary frequency and a different level when the messaging device isoperating in the secondary frequency.

FIGS. 11 and 12 depict frequency changes of a messaging device basedupon various operational conditions in accordance with non-limitingembodiments. Hysteresis is utilized in an attempt to avoid frequentswitching of operational frequency when the RSSI levels are near thethreshold values. FIG. 11 depicts three example operational scenariosfor a messaging device operating at the local frequency and generallycoordinates with the processing blocks 616, 618, 620 and 624 of FIG. 6.Referring first to Scenarios A and B, the messaging device determinesthat the frequency should be changed to the wide-area frequency due tothe occurrence of three average RSSI levels below the threshold (seeprocessing block 624 in FIG. 6), which indicates the local frequencysignal strength has a sufficient history of being too weak. WithScenario C, however, the operational frequency is not changed. As shown,the messaging device determines that there have been three instances ofthe average RSSI level being low, but since the messaging devicedetermined there were four instances of relatively strong signals, theoperational frequency of the device was not changed (see processingblocks 618 and 620 of FIG. 6). As is to be appreciated, while thethreshold average RSSI level is set at −110 dBm in FIG. 11 and FIG. 6,any suitable threshold average RSSI level can be used without departingfrom the scope of this disclosure.

FIG. 12 depicts three example operational scenarios for a messagingdevice operating at the secondary frequency and generally coordinateswith the processing blocks 722, 724, 726, 728 and 730 of FIG. 7.Referring first to Scenarios D and E, the messaging device determinesthat the frequency should be changed to the local frequency due to theoccurrence of three average RSSI levels below the threshold (seeprocessing block 726 in FIG. 7). With Scenario F, however, theoperational frequency is not changed. As shown, the messaging devicedetermines that there have been three instances of the average RSSIlevel being low, but since the messaging device determined there wereten instances of relatively strong signals, the operational frequency ofthe device was not changed (see processing blocks 728 and 730 of FIG.7). As is to be appreciated, while the threshold average RSSI level isset at −102 dBm in FIG. 12 and FIG. 7, any suitable threshold averageRSSI level can be used without departing from the scope of thisdisclosure.

FIG. 13 depicts a system block diagram of a messaging device 1300 inwireless communication with a computing device 1302. The computingdevice 1302 can be, for example, a smart phone, a tablet computer,personal computer, laptop computer, or other device with messagingfunctionality. The computing device 1302 can, for example, supportwireless wide area network (WWAN) data communications services includingInternet access. Examples of WWAN data communications services caninclude Evolution-Data Optimized or Evolution-Data only (EV-DO),Evolution For Data and Voice (EV-DV), CDMA/1×RTT, GSM with GeneralPacket Radio Service systems (GSM/GPRS), Enhanced Data Rates for GlobalEvolution (EDGE), High Speed Downlink Packet Access (HSDPA), High SpeedUplink Packet Access (HSUPA), and others. The computing device 1302 canprovide wireless local area network (WLAN) data communicationsfunctionality in accordance with the Institute of Electrical andElectronics Engineers (IEEE) 802.xx series of protocols, such as theIEEE 802.11a/b/g/n series of standard protocols and variants (alsoreferred to as “Wi-Fi”), the IEEE 802.16 series of standard protocolsand variants (also referred to as “WiMAX”), the IEEE 802.20 series ofstandard protocols and variants, and others. In some exampleembodiments, the computing device 1302 also can be arranged to performdata communications functionality in accordance with shorter rangewireless networks, such as a wireless personal area network (PAN)offering Bluetooth® data communications services in accordance with theBluetooth® Special Interest Group (SIG) series of protocols,specifications, profiles, and so forth. Other examples of shorter rangewireless networks can employ infrared (IR) techniques or near-fieldcommunication techniques and protocols, such as electromagneticinduction (EMI) techniques including passive or active radio-frequencyidentification (RFID) protocols and devices.

The computing device 1302 can comprise various radio elements, includinga radio processor, one or more transceivers, amplifiers, filters,switches, and so forth to provide voice and/or data communicationfunctionality. It can be appreciated that the computing device 1302 canoperate in accordance with different types of wireless network systemsutilize different radio elements to implement different communicationtechniques. The computing device 1302 also can comprise variousinput/output (I/O) interfaces for supporting different types ofconnections such as a serial connection port, an IR port, a Bluetooth®interface, a network interface, a Wi-Fi interface, a WiMax interface, acellular network interface, a wireless network interface card (WNIC), atransceiver, and so forth. The computing device 1302 can comprise one ormore internal and/or external antennas to support operation in multiplefrequency bands or sub-bands such as the 2.4 GHz range of the ISMfrequency band for Wi-Fi and Bluetooth® communications, one or more ofthe 850 MHz, 900 MHZ, 1800 MHz, and 1900 MHz frequency bands for GSM,CDMA, TDMA, NAMPS, cellular, and/or PCS communications, the 2100 MHzfrequency band for CDMA2000/EV-DO and/or WCDMA/JMTS communications, the1575 MHz frequency band for Global Positioning System (GPS) operations,and others.

The computing device 1302 can provide a variety of applications forallowing a user to accomplish one or more specific tasks using theembeddedness system 100. Applications can include, without limitation, aweb browser application (e.g., INTERNET EXPLORER, MOZILLA, FIREFOX,SAFARI, OPERA, NETSCAPE NAVIGATOR) telephone application (e.g.,cellular, VoIP, PTT), networking application, messaging application(e.g., e-mail, IM, SMS, MIMS, BLACKBERRY Messenger), contactsapplication, calendar application and so forth. The computing device1302 can comprise various software programs such as system programs andapplications to provide computing capabilities in accordance with thedescribed embodiments. System programs can include, without limitation,an operating system (OS), device drivers, programming tools, utilityprograms, software libraries, application programming interfaces (APIs),and so forth. Exemplary operating systems can include, for example, aPALM OS, MICROSOFT OS, APPLE OS, UNIX OS, LINUX OS, SYMBIAN OS, EMBEDIXOS, Binary Run-time Environment for Wireless (BREW) OS, JavaOS, aWireless Application Protocol (WAP) OS, and others.

A wireless communication link 1304 between the messaging device 1300 andthe computing device 1302 can be any suitable data transmission link,such as, a Bluetooth® link, a Wi-Fi link, NFC link, and so forth. Themessaging device 1300 can be configured to attempt to establish thewireless communication link 1304 whenever it is in proximity to thecomputing device 1302. Once a link has been established, the messagingdevice 1300 can be configured to transfer messages that are received bythe messaging device 1300 to the computing device 1302 via the wirelesscommunication link 1304. The computing device 1302 can include softwareinstructions stored within a memory 1306, which when executed by theprocessor 1308, which would allow an end user to view the message 1314on the computing device 1302. In some embodiments, the computing device1302 can also transmit replies, such as message statuses.

A return channel 1320 can allow for communication between the computingdevice 1302 and the server 1312. As is to be appreciated, the returnchannel 1320 can be routed through any suitable communications networks.The return channel 1320 can be used by the computing device 1302 toprovide messaging to the server 1312. The messaging could include anysuitable data, such as the status of the message 1314. Thus, thecomputing device 1302 can indicate the message was received, read,deleted, and so forth. In some embodiments, the messaging device 1300 isa one-way device yet two-way communication achieved by way of the returnchannel 1320 between the computing device 1302 and the server 1312.

In some embodiments, the computing device 1302 is configured to alertthe user of the message 1314 that is received on the messaging device1300. The alert on the computing device 1302 could be an audible alert,a visual alert, or various combinations thereof. With the computerdevice 1302 synced to the server 1312, the computing device 1302 canalso provide confirmation to the server 1312 indicating the receipt ofthe message 1314.

The messaging device 1300 can be in communication with a secondarystation transmitter 1310, which operates at a wide-area frequency. Inthe illustrated example, the messaging device 1330 is not incommunication with the primary station transmitter 1320 which operates alocal frequency. Both the secondary station transmitter 1310 and theprimary station transmitter 1320 are in communication with a messageserver 1312. The station transmitter 1310 can cause the transmission ofa message 1314, which may be a “one-to-many” message or a “one-to-one”message from both transmitters 1310 and 1320. The messaging device 1300will receive the messages 1314 from the secondary station transmitter1310.

FIG. 14 depicts an example block diagram 1400 of a server 1402 incommunication with a computing device 1408 and a messaging device 1412via a network 1406. Such configuration can be used, for example, toimplement OTIP, as described above. The server 1402 can execute anapplication 1404 which is stored in memory and is generally associatedwith messaging device account management. An exemplary protocol stack1410 is illustrated for the computing device 1408 and an exemplaryprotocol stack 1414 is illustrated for the messaging device 1412. In theillustrated embodiment, the computing device 1408 is electricallycoupled to the messaging device 1412 via a USB interface. Other types ofinterfaces can be used, such as wireless interfaces, for example. Thecomputing device 1408 can be any suitable device capable ofcommunicating with the messaging device 1412 and having a networkconnection to communicate with the network 1406. Example computingdevices 1408 can include, without limitation, a personal computer,tablet computer, smart phone, laptop computer, and so forth.

When the messaging device 1412 is plugged in to the USB port of thecomputer device 1408 (or otherwise coupled thereto), the messagingdevice 1412 can connect to a desktop application, as shown in theprotocol stack 1410. In some embodiments, the desktop application willprompt for device serial number and password, or other types of logincredentials. The person logging in to the desktop application may onlybe allowed to do certain functions based on a level of user rights.After the password is verified by accessing the messaging device 1412,the desktop application can use the serial number and the password, forexample, to connect to the application 1402 at the server 1402 throughthe network 1406. If a connection is not available, or cannot otherwisebe established, then access to the messaging device 1412 may be denied.In some embodiments, however, if a high level of access accompanies auser's login credentials, then a connection to the application 1402 atthe server 1402 is not necessarily required.

Various functionality can be implemented between the computing device1408 and the messaging device 1412 via the electrical coupling 1418. Forexample, using the desktop application executed on the computing device1408, the computing device 1408 can send various commands to themessaging device 1412 device, such as to set a parameter or to requestinformation. The messaging device 1412 can send commands to the desktopapplication, such as “receive message list” or “check for new firmware”.Moreover, in some embodiments, the desktop application can perform afirmware update process. It is noted that the desktop applicationexecuted on the computing device 1408 can provide security for all datareceived from the messaging device 1412, including anything that istemporally stored. The desktop application can also securely communicatewith the server 1402.

Communications between the computing device 1408 and the server 1402 caninclude, for example, setting/configuration updates for the messagingdevice 1412. The desktop application can also submit requests to theserver 1402 such as “get latest firmware version,” “download latestfirmware version,” and so forth. Communications between the computingdevice 1408 and the server 1402 can also include the uploading ofreceived messages lists and/or messaging device configurations.

The application 1404 executed by the server 1402 can provide variousfunctionality. In some embodiments, the application 1404 can sendcommands to the messaging device 1412 (through the computing device1408) to update its settings, configurations, and/or operationalparameters. The application 1404 can also send the latest version offirmware to the desktop application. The application 1404 can also storeone or more sets of complete configurations/parameters for a messagingdevice. Moreover, the application 1404 can receive and store updates toconfigurations of the messaging device 1412, as received from thedesktop application. The application 1404 can also respond to therequests, commands, and other types of messaging received from thedesktop application (e.g., to send the latest firmware version).

The examples presented herein are intended to illustrate potential andspecific implementations of the present disclosure. It can beappreciated that the examples are intended primarily for purposes ofillustration of the disclosure for those skilled in the art. Noparticular aspect or aspects of the examples are necessarily intended tolimit the scope of the present disclosure. For example, no particularaspect or aspects of the examples of system architectures, userinterface layouts, or screen displays described herein are necessarilyintended to limit the scope of the disclosure.

It is to be understood that the figures and descriptions of the presentdisclosure have been simplified to illustrate elements that are relevantfor a clear understanding of the present disclosure, while eliminating,for purposes of clarity, other elements. Those of ordinary skill in theart will recognize, however, that these sorts of focused discussionswould not facilitate a better understanding of the present disclosure,and therefore, a more detailed description of such elements is notprovided herein.

Any element expressed herein as a means for performing a specifiedfunction is intended to encompass any way of performing that functionincluding, for example, a combination of elements that performs thatfunction. Furthermore the disclosure, as may be defined by suchmeans-plus-function claims, resides in the fact that the functionalitiesprovided by the various recited means are combined and brought togetherin a manner as defined by the appended claims. Therefore, any means thatcan provide such functionalities may be considered equivalents to themeans shown herein.

In various embodiments, modules or software can be used to practicecertain aspects of the disclosure. For example, software-as-a-service(SaaS) models or application service provider (ASP) models may beemployed as software application delivery models to communicate softwareapplications to clients or other users. Such software applications canbe downloaded through an Internet connection, for example, and operatedeither independently (e.g., downloaded to a laptop or desktop computersystem) or through a third-party service provider (e.g., accessedthrough a third-party web site). In addition, cloud computing techniquesmay be employed in connection with various embodiments of thedisclosure.

Moreover, the processes associated with the present embodiments may beexecuted by programmable equipment, such as the messaging devicesdescribed herein. Software or other sets of instructions that may beemployed to cause programmable equipment to execute the processes may bestored in any storage device, such as, for example, a computer system(non-volatile) memory, an optical disk, magnetic tape, or magnetic disk.Furthermore, some of the processes may be programmed when the computersystem is manufactured or via a computer-readable memory medium.

It can also be appreciated that certain process aspects described hereinmay be performed using instructions stored on a non-transitorycomputer-readable memory medium or media that direct a computer orcomputer system to perform process steps. Non-transitorycomputer-readable medium may include, for example, memory devices suchas diskettes, compact discs of both read-only and read/write varieties,optical disk drives, and hard disk drives. A computer-readable mediummay also include memory storage that may be physical, virtual,permanent, temporary, semi-permanent and/or semi-temporary.

A “computer,” “computer system,” “host,” “engine,” or “processor” maybe, for example and without limitation, a processor, microcomputer,minicomputer, server, mainframe, laptop, personal data assistant (PDA),wireless e-mail device, cellular phone, pager, processor, fax machine,scanner, or any other programmable device configured to transmit and/orreceive data over a network. Computer systems and computer-based devicesdisclosed herein may include memory for storing certain softwareapplications used in obtaining, processing, and communicatinginformation. It can be appreciated that such memory may be internal orexternal with respect to operation of the disclosed embodiments. Thememory may also include any means for storing software, including a harddisk, an optical disk, floppy disk, ROM (read only memory), RAM (randomaccess memory), PROM (programmable ROM), EEPROM (electrically erasablePROM) and/or other computer-readable memory media.

In general, it will be apparent to one of ordinary skill in the art thatvarious embodiments described herein, or components or parts thereof,may be implemented in many different embodiments of software, firmware,and/or hardware, or modules thereof. The software code or specializedcontrol hardware used to implement some of the present embodiments isnot limiting of the present disclosure. For example, the embodimentsdescribed hereinabove may be implemented in computer software using anysuitable computer programming language such as .NET, SQL, MySQL, or HTMLusing, for example, conventional or object-oriented techniques.Programming languages for computer software and othercomputer-implemented instructions may be translated into machinelanguage by a compiler or an assembler before execution and/or may betranslated directly at run time by an interpreter. Examples of assemblylanguages include ARM, MIPS, and x86; examples of high level languagesinclude Ada, BASIC, C, C++, C#, COBOL, Fortran, Java, Lisp, Pascal,Object Pascal; and examples of scripting languages include Bournescript, JavaScript, Python, Ruby, PHP, and Perl. Such software may bestored on any type of suitable computer-readable medium or media suchas, for example, a magnetic or optical storage medium. Thus, theoperation and behavior of the embodiments are described without specificreference to the actual software code or specialized hardwarecomponents. The absence of such specific references is feasible becauseit is clearly understood that artisans of ordinary skill would be ableto design software and control hardware to implement the embodiments ofthe present disclosure based on the description herein with only areasonable effort and without undue experimentation.

While various embodiments of the disclosure have been described herein,it should be apparent, however, that various modifications, alterationsand adaptations to those embodiments may occur to persons skilled in theart with the attainment of some or all of the advantages of the presentdisclosure. The disclosed embodiments are therefore intended to includeall such modifications, alterations and adaptations without departingfrom the scope and spirit of the present disclosure as set forth in theappended claims.

We claim:
 1. A method, comprising: electronically coupling a messagingdevice to a computing device via a Universal Serial Bus (USB) interface,the messaging device locally storing a plurality of messages and aplurality of Channel Access Protocol (CAP) codes in a memory of themessaging device, wherein a first of the plurality of CAP codes uniquelyidentifies the messaging device and a second of the plurality of CAPcodes identifies the messaging device as a member of a first messagedistribution group, and wherein the messaging device is operational on aprimary operational frequency and a secondary operational frequency;subsequent to the messaging device being added to a second messagedistribution group associated with a group CAP code comprising aplurality of existing messaging devices each of the plurality ofexisting messaging devices respectively storing the group CAP code inmemory of the existing messaging device, receiving by the messagingdevice from the computing device a test communication through thecoupling via the USB interface to confirm the addition of the messagingdevice to the second message distribution group without communicatingwith the plurality of existing messaging devices storing the group CAPcode; and when the test communication is successfully received by themessaging device, indicating by the messaging device receipt of the testcommunication.
 2. The method of claim 1, comprising: charging a powersource of the messaging device through an electrical charge receivedthrough the coupling.
 3. The method of claim 1, wherein indicatingreceipt of the test communication comprises providing at least one of avisual alert and an audible alert.
 4. The method of claim 1, comprising:receiving an update to firmware of the messaging device from thecomputing device via the coupling.
 5. The method of claim 4, wherein thecomputing device is in communication with a host through a networkconnection and the update to the firmware is received from the host bythe computing device.
 6. A messaging device, comprising: a UniversalSerial Bus (USB) data interface; a rechargeable power source; a chargingsystem operatively coupled to the USB data interface and therechargeable power source; a processor operatively coupled to therechargeable power source; and a non-transitory computer readable mediumlocally storing a plurality of Channel Access Protocol (CAP) codes,wherein a first of the plurality of CAP codes uniquely identifies themessaging device and a second of the plurality of CAP codes identifiesthe messaging device as a member of a first message distribution group,the computer readable medium having instructions stored thereon, whichwhen executed by the processor cause the processor to: receive messageson one of a primary operational frequency and a secondary operationalfrequency, wherein the primary operational frequency is associated witha private network and the secondary operational frequency is associatedwith a public carrier network using a synchronous paging protocol;receive programming updates through the USB data interface; receive anelectrical charge through the USB data interface; subsequent to themessaging device being added to a second message distribution groupassociated with a group CAP code comprising a plurality of existingmessaging devices each of the plurality of existing messaging devicesrespectively locally storing the group CAP code, receive from acomputing device a test communication through the USB data interface totest an operation of the messaging device and confirm the addition ofthe messaging device to the second message distribution group withoutcommunicating with the plurality of existing messaging devices storingthe group CAP code; and when the test communication is successfullyreceived, indicate receipt of the test communication.
 7. The messagingdevice of claim 6, further comprising a wireless communicationinterface.
 8. The messaging device of claim 7, wherein the wirelesscommunication interface supports a near-field wireless communicationprotocol.
 9. The messaging device of claim 7, wherein the instructions,which when executed by the processor cause the processor to: wirelesslytransfer a message using the wireless communication interface to thecomputing device.
 10. The messaging device of claim 6, wherein theprimary operational frequency and the secondary operational frequencyare both within the range of 929-932 MHz.
 11. The messaging device ofclaim 6, wherein receipt of the test communication is indicated by atleast one of a visual alert and an audible alert.
 12. The messagingdevice of claim 6, wherein the instructions, which when executed by theprocessor cause the processor to: receive an update to an encryptionkey.
 13. The messaging device of claim 12, wherein the computing deviceis in communication with a host through a network connection and theupdate to the encryption key is received from the host by the computingdevice.
 14. A method, comprising: electronically coupling a messagingdevice to a computing device via a Universal Serial Bus (USB) interface,the messaging device locally storing a plurality of messages and aplurality of Channel Access Protocol (CAP) codes in a memory of themessaging device, wherein a first of the plurality of CAP codes uniquelyidentifies the messaging device and a second of the plurality of CAPcodes identifies the messaging device as a member of a first messagedistribution group; updating firmware of the messaging device based ondata received from the computing device via the coupling; subsequent tothe messaging device being added to a second message distribution groupassociated with a group CAP code comprising a plurality of existingmessaging devices each of the plurality of existing messaging devicesrespectively storing the group CAP code in memory of the existingmessaging device, receiving by the messaging device from the computingdevice a test communication through the coupling via the USB interfaceconfirming the addition of the messaging device to the second messagedistribution group, wherein the test communication is not communicatedto the plurality of existing messaging devices storing the group CAPcode; subsequent to the successful receipt of the test communication,operating the messaging device at a first operational frequency; anddetermining a first filtered average received signal strength indication(RSSI) level of the first operational frequency based on a firstplurality of measured RSSI levels, wherein only measured RSSI levelsthat are within a target RSSI range are included in the first pluralityof measured RSSI levels.
 15. The method of claim 14, comprising:incrementing the value of a first variable when the determined firstfiltered average RSSI level of the first operational frequency is abovea first threshold RSSI level; reducing the value of a second variablewhen the value of the first variable is at a first threshold value;incrementing the value of the second variable when the determined firstfiltered average RSSI level of the first operational frequency is belowthe first threshold RSSI level; and operating the messaging device at asecond operational frequency when the value of the second variable is ata second threshold value.
 16. The method of claim 14, wherein thecomputing device is in communication with a host through a networkconnection and the update to the programming is received from the hostby the computing device.
 17. The method of claim 14, comprising:charging a power source of the messaging device through an electricalcharge received through the coupling.
 18. The method of claim 14,wherein indicating receipt of the test communication comprises providingat least one of a visual alert and an audible alert.
 19. The method ofclaim 14, wherein electronically coupling the messaging device to thecomputing device comprises wirelessly coupling the messaging device tothe computing device via an wireless interface.